Conformance checking

Conformance checking is a process mining technique that takes an existing process model and compares it with an event log of the same process.[1] Conformance checking can be used to check if reality, as recorded in the log, conforms to the model and vice versa. For instance, there may be a process model indicating that purchase orders of more than one million Euro require two checks. Analysis of the event log will show whether this rule is followed or not. Another example is the checking of the socalled “four-eyes” principle stating that particular activities should not be executed by one and the same person. By scanning the event log using a model specifying these requirements, one can discover potential cases of fraud. Hence, conformance checking may be used to detect, locate and explain deviations, and to measure the severity of these deviations.

Contents

Overview

Unlike process discovery, conformance checking takes both a model and event log as a starting point. While conducting a conformance check the behavior of a process model and the behavior recorded in an event log are compared to find commonalities and discrepancies. Such analysis may result in global conformance measures (e.g., 85% of the cases in the event log can be replayed by the model) and local diagnostics (e.g., activity x was executed 15 times although this was not allowed according to the model). The interpretation of non-conformance depends on the purpose of the model. If the model is intended to be descriptive, then discrepancies between model and log indicate that the model needs to be improved to capture reality better. If the model is normative, then such discrepancies may be interpreted in two ways. Some of the discrepancies found may expose undesirable deviations, i.e., conformance checking signals the need for a better control of the process. Other discrepancies may reveal desirable deviations. For instance, workers may deviate to serve the customers better or to handle circumstances not foreseen by the process model.

Techniques and Metrics

Most conformance checking techniques are based on the principle of Replay, i.e., the event log is replayed on the process model. For example, while replaying an event log on a Petri net, one can count the number of missing and remaining tokens. Alternatively, one can try to optimize the mapping of traces onto models by introducing costs associated to skipping, ingnoring, or swapping events in the log and/or model.

Typical conformance metrics are:

References

  1. ^ Process Mining Webpage (www.processmining.org)

Further reading

External links